Skip to content

Copilot: a beta on Free and Pro, four helps, honest about what is sent - #295

Merged
xuelink merged 1 commit into
mainfrom
claude/copilot-copy-refresh-def7d1
Oct 25, 2026
Merged

xuelink merged 1 commit into
mainfrom
claude/copilot-copy-refresh-def7d1

Conversation

@xuelink

@xuelink xuelink commented Oct 25, 2026 •

Copy link
Copy Markdown
Member

Do not merge until copilot.langx.io is live. Several lines link to it. The owner's other session merges this, together with langx/docs#61.

Brings every public Copilot claim on langx.io in line with the app's Copilot on langx/langx main, using the verified fact sheet (FACTS-app-copilot.md, section 8 items 1–10) and the owner's decisions of 25 October 2026:

  • Copilot is in the app now as a beta, for every account with a verified email, on Free and Pro. No "rolling out", "may not be on for your account yet" or Pro-only wording.
  • No allowance numbers. Every plan has a daily allowance, Pro's is larger, and the app shows what is left.
  • The four helps have the app's names: Check my sentence, Say it in {language}, Explain, Reply ideas.
  • Privacy: never "private" or "only you see it". The person you talk to sees none of Copilot's answers. Explain and Reply ideas send the other person's words to Anthropic, after a consent sheet. Copilot turns off in Settings, and answers can be reported.

Each changed claim

Where Was Now Why
src/lib/data/faq.ts "What is LangX Copilot?" (also on /faq and in /llms.txt) "Private AI help", three helps, "Only you see it", "in Pro… rolling out… may not be on for your account yet" Four helps by name; in the app as a beta on Free and Pro; partner sees none of it; what goes to Anthropic, including the other person's words for Explain and Reply ideas; consent sheet first; turn off in Settings; report any answer; daily allowance, Pro's larger; link to copilot.langx.io Fact sheet §1–§4; items 1 and rule 15
src/routes/plans/+page.svelte FAQ "What does Pro add?" "private AI help… in Pro… rolling out… may not be on for your account yet" "a beta on both plans, and Pro's daily allowance is larger" Item 2
src/lib/data/plans.ts /plans comparison No Copilot row Row Copilot · Beta: Free "Daily allowance", Pro "Larger allowance" The app's comparison has a Copilot row (item 2). See note 1 below
src/routes/(site)/compare/+page.svelte FAQ "…different from an AI tutor?" "private AI help with your own messages, is in Pro… rolling out" "an AI helper in the chat, a beta on Free and Pro: it helps you write and understand messages in a chat with a person, and it does not talk with you" Item 3. Explain and Reply ideas work on the partner's words, so "your own messages" was wrong
Blog: memrise, bilingua (×2), babbel, praktika, speak "(in Pro… rolling out) helps with your own messages" "(a beta, on Free and Pro) helps you write and understand messages in a chat with a person"; "it does not talk with you / teach you" kept Item 4
Blog: best-language-exchange-apps-2027 (table, "What is new", cons, FAQ), …-for-beginners (table, limits), ai-conversation-partner-vs-language-exchange, duolingo-alternatives-for-speaking "Copilot on Pro (beta, rolling out)", "private AI help", "may not be on for every account yet" "a beta on Free and Pro", "still a beta" in the drawbacks lists; the 2027 "What is new" paragraph names the four helps and links copilot.langx.io Item 5
Blog: best-language-exchange-apps (drawbacks) "AI help (LangX Copilot) is in Pro as a beta, rolling out gradually" "LangX Copilot, the AI helper in the chat, is still a beta" The same stale line, not in the fact sheet's list
AMA post, editor's note "(Update, 21 October 2026: … LangX Copilot is in it [Pro] as a beta, rolling out gradually.)" "(Update, 25 October 2026: … in the app as a beta, on Free and Pro. It is not the v1 feedback described below…)" with a link Item 6. The 2024 text and the 23 September note are left as written
"LangX v2: what changes and why" "(Update, 21 October 2026: … now in Pro as a beta, rolling out gradually.)" "(Update, 25 October 2026: … now in the app as a beta, on Free and Pro; copilot.langx.io describes it.)" Item 7. The August text is left as written
WelcomeBack.svelte (/welcome-back) "in Pro now as a beta, rolling out gradually" "in the app now as a beta, on Free and Pro" Item 8
src/lib/data/features.ts (rendered nowhere) "Private AI help with your messages", tags Pro + "Beta, rolling out" "An AI helper in the chat, on Free and Pro, that waits for your tap", tag "Beta" Item 10
src/routes/llms.txt/+server.ts No Copilot link "LangX Copilot" line pointing to copilot.langx.io, under "The app" Item 20: nothing pointed to the new site
PRODUCT.md (writer guidance, not rendered) "beta, rolling out: on only for some accounts so far" Copilot moved out of the Pro list into its own fact bullet, with the wording rules above Item 9
docs/seo/writing-guide.md (writer guidance, not rendered) "private AI help… in Pro… rolling out" (two lines) "a beta on Free and Pro", never private, never "rolling out", no numbers Not in the fact sheet's list. Fixed so new posts don't reintroduce the old wording

The privacy policy was already correct (#294) and is not touched. Header.svelte and Footer.svelte are not touched; claude/header-subsite-links changes them.

Notes for the reviewer

  1. The /plans row differs from the app's paywall on purpose. The app's comparison shows "AI copilot", a dash on Free and "Beta" on Pro, from PLAN_LIMITS.free.copilot = false. The server gives Free an allowance (copilotPer24h), and the owner decided the site says Free and Pro. The row follows the server, without numbers, and a comment in plans.ts says why.
  2. "Say it in {language}" on a public page. The braces would read like a template bug, so the FAQ writes "Say it in Spanish (or whichever language you are learning)". PRODUCT.md keeps {language}.
  3. Dated updates were replaced, not stacked. The 21 October updates on the AMA and v2 posts now read 25 October, because what they said had stopped being true. The original text and the 23 September note are unchanged.
  4. updated: dates are not bumped, the same as in the 21 October sweep (3e921c2).
  5. Out of scope, left as is: the free-week wording (fact sheet item 11). The Terms say monthly and yearly both start with a free week, while /plans, prices.ts and the store listing say yearly only (TermsAndConditions.md:41). Also not Copilot: docs/seo/writing-guide.md:25 still gives Fluent and Polyglot translation limits.

Checks

  • npm ci, then under Node 22: npm run check (0 errors, 0 warnings) and npm run build (exit 0, 1373 Markdown pages).
  • npx prettier --check on every changed file: clean.
  • The built site contains none of "rolling out", "only you see it", "private AI help", "may not be on for your/every account" or "Copilot on Pro".
  • Checked in npm run dev: /faq (the Copilot answer), /plans (the new row on desktop and at 375 px, no horizontal scroll; the FAQ), /compare, /welcome-back, and the AMA, v2, 2027 and Bilingua posts.

🤖 Generated with Claude Code

The app's Copilot is now on for every account with a verified email, on
Free and Pro, with a daily allowance on each plan (Pro's is larger). The
allow-list is gone, so "rolling out", "may not be on for your account yet"
and "in Pro" no longer describe it, and "private" / "only you see it" never
did: Explain and Reply ideas send the other person's words to Anthropic.

The FAQ answer (also on /faq and in /llms.txt) now names the four helps as
the app does, says what goes to Anthropic and when, that it turns off in
Settings and answers can be reported, and links to copilot.langx.io. The
/plans FAQ and /compare FAQ, the blog lines, WelcomeBack and the unused
features card follow. /plans gains the app's Copilot row, with the server's
allowance on both plans rather than the paywall's dash, and no numbers. The
AMA and v2 posts keep what they said at the time; their dated updates now
read 25 October. PRODUCT.md and the SEO writing guide carry the new rules so
later posts do not copy the old wording back in.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@xuelink
xuelink merged commit f62eb8a into main Oct 25, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant